翻訳と辞書
Words near each other
・ Plug-in electric vehicles in Norway
・ Plug-in electric vehicles in the Netherlands
・ Plug-in electric vehicles in the United Kingdom
・ Plug-in electric vehicles in the United States
・ Plug-in hybrid
・ Plug-in Hybrid Electric Vehicle Research Center
・ Plug-in hybrids in California
・ Plug-in hybrids in New York
・ Plug-in vehicle
・ Plug.dj
・ Plugari
・ Plugawice
・ Plugboard
・ Plugd Records
・ Plugg
Pluggable authentication module
・ Pluggable Authentication Service
・ Pluggable look and feel
・ Pluggd
・ Plugge
・ Plugge's Plateau Commonwealth War Graves Commission Cemetery
・ Plugged (novel)
・ Plugged In
・ Plugged In (album)
・ Plugged in Permanent
・ Plugged Nickle
・ Plugged Tour
・ Plugged!
・ Plugger
・ Pluggers


Dictionary Lists
翻訳と辞書 辞書検索 [ 開発暫定版 ]
スポンサード リンク

Pluggable authentication module : ウィキペディア英語版
Pluggable authentication module

A pluggable authentication module (PAM) is a mechanism to integrate multiple low-level authentication schemes into a high-level application programming interface (API). It allows programs that rely on authentication to be written independently of the underlying authentication scheme. PAM was first proposed by Sun Microsystems in an Open Software Foundation Request for Comments (RFC) 86.0 dated October 1995. It was adopted as the authentication framework of the Common Desktop Environment. As a stand-alone open-source infrastructure, PAM first appeared in Red Hat Linux 3.0.4 in August 1996. PAM is currently supported in the AIX operating system, DragonFly BSD,〔(PAM manual page of DragonFly BSD )〕 FreeBSD, HP-UX, Linux, Mac OS X, NetBSD and Solaris.
Since no central standard of PAM behavior exists, there was a later attempt to standardize PAM as part of the X/Open UNIX standardization process, resulting in the X/Open Single Sign-on (XSSO) standard. This standard was not ratified, but the standard draft has served as a reference point for later PAM implementations (for example, OpenPAM).
==Criticisms of PAM==
Since most PAM implementations do not interface with remote clients themselves, PAM on its own cannot implement Kerberos, the most common type of SSO used in Unix environments. This led to SSO's incorporation as the "primary authentication" portion of the would-be XSSO standard and the advent of technologies such as SPNEGO and SASL. This lack of functionality is also the reason SSH does its own authentication mechanism negotiation.
In most PAM implementations, pam_krb5 only fetches Ticket Granting Tickets, which involves prompting the user for credentials and are only used for initial login in an SSO environment. To fetch a service ticket for a particular application, and not prompt the user to enter credentials again, that application must be specifically coded to support Kerberos, as pam_krb5 cannot itself get service tickets, although there are versions of PAM-KRB5 that are attempting to work around the issue.〔(PAM-KRB5 )〕

抄文引用元・出典: フリー百科事典『 ウィキペディア(Wikipedia)
ウィキペディアで「Pluggable authentication module」の詳細全文を読む



スポンサード リンク
翻訳と辞書 : 翻訳のためのインターネットリソース

Copyright(C) kotoba.ne.jp 1997-2016. All Rights Reserved.